adding matrix testing for db #496
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduces matrix testing for various databases in our CI pipeline, significantly enhancing our testing strategy. By adding dedicated jobs for SQLite, PostgreSQL, MySQL, Microsoft SQL Server, and Oracle, we ensure that our code is compatible across multiple database systems.
Motivation:
Increased Coverage: The addition of matrix testing allows us to run our test suite against different database backends, ensuring that any database-specific issues are caught early in the development process.
Improved Reliability: By testing against multiple versions of Python and various database systems, we can guarantee that our application behaves consistently and correctly across environments, reducing the risk of production issues.
Encouraging Best Practices: This change encourages better coding practices by requiring that all interactions with the database are robust and well-tested, as we can identify failures specific to each database type.
Future-proofing: As we expand our application, supporting multiple databases ensures that we can cater to a wider audience, making our project more versatile and adaptable to different user needs.
Changes:
This enhancement will lead to a more robust and versatile codebase, ultimately improving the overall quality of the project.